Repository navigation
Document the queue worker job timeout for workflow tasks - #578
Merged
Merged
Conversation
With pcntl, queue:work kills a job after --timeout seconds (60 by default). A workflow task killed that way is rolled back and retried after its lease expires, so a task that always needs longer never completes (durable-workflow/workflow#1231). Document running workflow workers with --timeout=0 or above the longest workflow task in Running Workers, and link it from every page that starts a workflow worker. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Mirror the English Worker timeout subsection in Installation and the links to
it from the quickstart, sample app, Laravel adoption and microservices guides
into de, es, fr, ja, pt-BR, uk and zh-Hans, keeping the {#worker-timeout}
anchor, commands and config keys unchanged. Record the reviewed English source
hashes for the five guides in each locale's source-hashes.json.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
A blanket --timeout=0 lets a hung activity hold its worker forever and breaks Laravel's rule that retry_after exceeds every job's timeout. Explain how the workflow task timeout, the task lease and retry_after relate, and recommend a dedicated workflow-task connection (retry_after above the lease, workers with --timeout below it) with activities on a bounded queue. Note that newer releases give workflow task jobs this timeout themselves. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Replace the Worker timeout subsection of Installation in de, es, fr, ja,
pt-BR, uk and zh-Hans with a translation of the rewritten English section:
how the workflow task timeout, the task lease and retry_after relate, the
dedicated workflow-task connection, and the newer-release behaviour. Code
blocks and the {#worker-timeout} anchor are unchanged. Record the reviewed
English installation.md hash in each locale's source-hashes.json.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The workflow task job timeout is opt-in from Workflow 2.34.0; by default the worker's --timeout applies. Drop the claim that work past the lease cannot complete, say that killed tasks are counted as lost leases, and route activities to the bounded worker through the activity's $queue. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Documents the queue worker job timeout for workflow tasks (durable-workflow/workflow#1231, durable-workflow/workflow#1244).
With the
pcntlextension,queue:workkills a job after--timeoutseconds, which defaults to 60. A workflow task killed that way is rolled back and retried after its lease expires. A workflow task that always needs longer, such as one scheduling or finishing a wideall(), never completes.installation.mdgets a new Worker timeout section ({#worker-timeout}) under Running Workers. A killed workflow task is retried only after its lease expires and is counted as a lost lease. The workers serving workflow tasks need a timeout that covers the longest workflow task, withretry_afterabove it, while activities keep a bounded timeout on their own queue: the example sets the activity class's$queueso the bounded worker actually receives activities. Horizon'stimeoutis the same setting. It describes the opt-inDW_V2_WORKFLOW_TASK_JOB_TIMEOUT_SECONDSand the worker-start warning added in Workflow 2.34.0.quickstart.md,sample-app.md,laravel-adoption.md(embedded v2 worker) andconfiguration/microservices.md.ensuring-same-server.mdonly starts activity workers and is unchanged.source-hashes.jsonis updated.check-doc-translations.jspasses withDOCS_TRANSLATION_BASEset to themaincommit, as doescheck-doc-translation-updates.test.js.🤖 Generated with Claude Code